Search on my Exchange 2013 is not working. Event 1009 with source MSExchangeFastSearch is logged in the Application log:

The indexing of mailbox database MB01 encountered an unexpected exception. Error details: Microsoft.Exchange.Search.Core.Abstraction.OperationFailedException: The component operation has failed. ---> Microsoft.Exchange.Search.Fast.FastConnectionException: Connection to the Content Submission Service has failed. ---> Microsoft.Ceres.External.ContentApi.ConnectionException: Given CSS specification failed:

Could not connect to CSS node at net.tcp://localhost:17028/ContentSubmissionServices/content with flow: Microsoft.Exchange.Search.WatermarkWriter.12.14. Error: Object reference not set to an instance of an object. Inner exception:---

   at Microsoft.Ceres.External.ContentApi.DocumentFeeder.DocumentFeeder.SetCssNodes(IEnumerable`1 newCssNodes)

   at Microsoft.Ceres.External.ContentApi.DocumentFeeder.DocumentFeeder..ctor(DocumentFeederOptions options)

   at Microsoft.Exchange.Search.Fast.FastFeeder.Initialize()

   --- End of inner exception stack trace ---

   at Microsoft.Exchange.Search.Fast.FastFeeder.Initialize()

   at Microsoft.Exchange.Search.Fast.Factory.InternalCreateFastFeeder(ISearchServiceConfig config, String indexSystemFlow, String indexSystemName, String instanceName, Int32 numberOfSessions)

   at Microsoft.Exchange.Search.Fast.FeederStateStorage.SendWatermarkUpdateToFast(Int64 fastId, Int64 watermark)

   at Microsoft.Exchange.Search.Fast.FeederStateStorage.SetMailboxCrawlerState(MailboxCrawlerState state)

   at Microsoft.Exchange.Search.Mdb.FeederStateInitializer.EnsureInitialStateSet()

   at Microsoft.Exchange.Search.Engine.SearchFeedingController.InternalExecutionStart()

   at Microsoft.Exchange.Search.Core.Common.Executable.InternalExecutionStart(Object state)

   --- End of inner exception stack trace ---

   at Microsoft.Exchange.Search.Core.Common.Executable.EndExecute(IAsyncResult asyncResult)

   at Microsoft.Exchange.Search.Engine.SearchRootController.ExecuteComplete(IAsyncResult asyncResult)>

All Exchange services are running, I even created a new mailbox and the same error happens. I'm running Exchange 2013 on Server 2012.

Hello,

Is it convenient for you to create another MBX role, create new DB on it and check whether the issue still occur?

Thanks,

Simon Wu

Exchange Forum Support

Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

• Edited by Simon_WuMicrosoft contingent staff, Moderator Wednesday, November 21, 2012 6:56 AM

Thanks for the suggestion. I'm afraid that's not really an option, I need to fix the error on this server.

Hi Jetze, 

I had the same issue on an Exchange Server 2013 (CAS+MBX) a DAG member running on Windows Server 2012. Even all the services were running the ContentIndexState showed as Failed. After rebooting the server and then running the Update-MailboxDatabaseCopy with -CatalogOnly switch resolved my issue. Before the reboot this command didn't work either.

You may have already tried rebooting the server but wanted to let you know above steps resolved my issue. 

Thanks.

CK

Hi

try to run for your server this:

Get-MailboxDatabaseCopyStatus -server mxserver | fl name, contentindexstate

as a mxserver use every server of Exchange DAG.

 

if you find contentindexstate failed for any database then run this for database:

Update-MailboxDatabaseCopy "MxDatabase\mxserver" -CatalogOnly

I had an issue with mailbox databases copies

The content index state always showed as failed

I found out that the setup /preparead does not add a group ContentSubmitters

 

http://support.microsoft.com/kb/2807668

 

Ok well we didnt have multiple copies of the database, only one copy, however i did receive a similar error and search was working poorly, not finding things, primarily in webmail.

So incase someone else is here looking for the same info, i was able to fix my single server single database install with the following info:

http://theucguy.net/fix-corrupted-content-index-catalog-of-a-mailbox-database-with-single-copy/

TLDR: Stop microsoft exchange search, stop exchange search host controller, go into the content DB folders (D:\Data\Mailboxes\Ex0 for me) and delete the folder in there with the GUID that ends in .single.

Restart the services and after a few minutes, "get-mailboxdatabasecopystatus | ft -autosize" will switch from FAILED to crawling and then eventually healthy. This process may take a few hours.

hope it helps